The latest release information about the Web Forms for Marketers module version 2.3.
1. Release History
Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.
June 23, 2014
The Web Forms for Marketers module 2.3 rev.140617 is released.
Tested with Sitecore CMS 6.6 rev.130111 (Update-3) and 7.0 rev. 140408
Compatibility
This version of the module runs on Sitecore CMS 6.5, 6.6 and 7.0.
Note: to run the WFFM on CMS 7.0 see the workaround in the Known Issues.
Change log.
Issues resolved:
- Form reports
- An issue which cause exception on switching pages in reports is fixed (379538)
- Uploaded File is now represented as a link in the report (367409)
- Fields and validation
- "Required" validation is now supported for the "Checkbox" field (353574)
- DatePicker value is now inserted into e-mail in a user friendly format (370324)
- An issue which cause an exception in 'List Items' dialog is fixed (386529)
- Form Designer
- Error when trying to open form item with dash in the name (402236)
- An issue with scrolls in ListItemsEditor dialogue which cause disappearing dialogue buttons is fixed (350191)
- Send mail editor saves values added by insert field drop down (351284)
- 'Save/Close' and 'Close' buttons of the Form Designer works in the Content Editor mode (405268)
- Select existing goal wizard allows to select goal in the deep tree (383066)
- Multisite
- A new setting was added that allow using different themes on multisite solution. (318929)
- Common issues
- An issue with multiple lines text in a mail is fixed (372135)
- Theme and Color can be set on a form folder for all sub forms (334526)
December 10, 2013
The Web Forms for Marketers module 2.3.0 rev.131126 is released.
Tested with Sitecore CMS 6.6 rev.130111 (Update-3) and 7.0 rev. 130918 (Update-2).
Compatibility
This version of the module runs on Sitecore CMS 6.5, 6.6 and 7.0.
Note: to run the Web Forms for Marketers module on CMS 7.0, see the workaround in the Known Issues section.
Change log.
New features
- A new “From” field has been introduced in the Send Mail Editor dialog (323627).
Issues resolved:
- Save Actions
- The Send Mail Editor dialog now uses field titles as tokens for replacement instead of field names (322385).
- Verification Actions
- Verification actions ignored localized parameters field (376093).
- An issue with duplicating the “Access Security Risk” item after upgrading the module from version 2.2 to 2.3 has been fixed (369608).
- Form Reports
- An issue which caused placing data into inappropriate columns in Form Reports has been fixed (337062, 357531).
- Fields and Validation
- An issue which caused exception after clearing “Selected Value” in list-type fields has been fixed (362611).
- The Email validator could make the page freeze if more than 50 letters entered to the Email form field (366333).
- Language issues
- An issue with displaying untranslated form fields and the Submit button has been fixed (364472).
- Missed translations for the module interface in the Swedish translation package were added (394709).
- Common issues
- An issue which prevented the “Restricting Placeholders” dialog from showing placeholder settings items that are located in subfolders has been fixed (362149).
- An issue which caused an incorrect redirection after a web form submitting fixed. Now the module uses link manager to generate a link to redirect the user to (328900, 334022, 352537).
- Form Designer showed incorrect redirection URL after a web form submitting. Now it shows the correct URL that the user will be redirected to (356426, 392671).
- Field Properties Editor in Form Designer was displayed incorrectly in Chrome (392414).
- An issue which caused an exception after submitting a form due to non-action child items under the /sitecore/system/Modules/Web Forms for Marketers/Settings/System/System Action folder has been fixed (358042).
- An issue which caused incorrect renderring of a web form in the Chrome browser has been fixed (377471).
January 31, 2013
The Web Forms for Marketers module 2.3.0 rev.130118 is released.
Tested with Sitecore CMS 6.6 Update-3 rev.130111 and CMS 7.0 rev. 130424.
Compatibility
This version of the module runs on Sitecore CMS 6.5, 6.6 and 7.0.
Note: for running WFFM on CMS 7.0 see workaround in the Known Issues
Change log.
Important changes
- Default database has been changed from SQLite to MSSQL. Configuration steps have been added to the installation readme.
Issues resolved:
- WFFM roles
- An issue which caused absence of the WFFM shortcut in the Sitecore Menu for a user with Marketer Form Author role has been fixed (335511).
- An issue which prevented a user with Marketer Form Author role to change Restricting Placeholders has been fixed (371169).
- Performance & Error Handling
- An issue which caused performance to decrease while using a form with Dropout Tracking has been fixed (367165).
- An issue which caused spurious appearances of error message in logs while using WFFM with disabled analytics has been fixed (356307).
- Adding forms in the Page Editor
- An issue which caused the Page Editor to fail if MVC and WFFM were installed on CMS 6.6 has been fixed (376196).
- An issue which prevented adding a form using the Page Editor when Datasource Location field is empty or contains non-existing path has been fixed (352647).
- Save Actions
- An issue which prevented submitting a form while using Create User action when e-mail is used as User Name has been fixed (365281).
- An issue which prevented the EditRoleMembership action from creating a new user has been fixed (365399).
- Fields and Validation
- An issue which caused List field types to be incorrectly displayed in Firefox and Chrome browsers has been fixed (365455).
- An issue which caused an error message while trying to request the image source attribute from the Captcha field type has been fixed (364793).
- An issue preventing a form that has been converted to a layout from being submitted if there were more than 256 characters in the form has been fixed (344731).
- Architectural and Support issues
- An issue which caused several Form Reports to work incorrectly CMS 6.6 has been fixed (376689, 362936).
- Language issues
- Several issues that caused languages to be used and recorded incorrectly in WFFM have been fixed (316682, 344233, 343557, 354215).
- Common issues
- An issue preventing a site page with a form from being rendered when internet connection is slow on IE6, IE7 and Windows XP has been fixed (364359).
- An issue which caused data to be exported from the Form Designer with incorrect time zones has been fixed (327435).
- An issue which prevented the Submit button style from being modified using a CSS class has been fixed (333342).
April 3, 2012
The Web Forms for Marketers module 2.3.0 rev.120216 is released.
Tested with Sitecore CMS 6.5.0 Update-3 rev. 111230.
Important: Web Forms for Marketers 2.3.0 is compatible with Sitecore CMS 6.5 (rev. 110602) or later. This version is not compatible with versions of Sitecore CMS earlier than 6.5.
Important changes
- Danish translations have been improved in this update.
Issues resolved
- Architectural and Support issues
- An issue which caused Web Forms for Marketers not to work with MS SQL Server 2008 has been fixed (363045).
December 19, 2011
The Web Forms for Marketers module 2.3.0 rev.111209 is released.
Tested with Sitecore CMS 6.5.0 rev. 111123.
Important: Web Forms for Marketers 2.3.0 is compatible with Sitecore CMS 6.5 (rev. 110602) or later. This version is not compatible with versions of Sitecore CMS earlier than 6.5.
New Features
- A new Form Verification “Assess Security Risk” has been added, which is enabled by default. This evaluates entered form data to ensure it does not contain scripts or similar data which could pose a security risk. (351475, 352696).
Important changes
- Web Forms for Marketers has been optimized to work with SQLServer session state mode. (344736, 356676)
Issues resolved
-
Save Actions
- An issue which caused appearance of error message while using Send Standard Message action in ASYNC mode has been fixed (352172).
- An issue which caused empty dropdown list in the Send Mail action under Japanese version has been fixed (352176).
- An issue which caused incorrect saving of the inserted fields to the body of the message in the Send Mail action has been fixed (352175).
- Dynamic CRM Integration
An issue which caused problems with CRM Save Actions while connecting to the European and Asian services of CRM Online 2011 has been fixed (352170).
- An issue causing impossible mapping fields in CRM Save Action has been fixed (354196).
- An issue which caused WFFM module not to connect to CRM online when Application Pool identity is NETWORK SERVICE has been fixed (350396).
- An issue causing CRM security provider to fail at initialization in some cases due to a dependency on specific assembly versions has been fixed (352169).
- Fields and Validation
- An issue which caused missing icons in the Captcha field type on the Content Delivery server has been fixed (352165).
- An issue which caused appearance of an extra warning message while using Multi-Line text field type with default MaxLength value has been fixed (352179).
- An issue causing incorrect converting of some symbols in the Regular Expression field of the Multi-Line text field type has been fixed (352177).
- An issue which caused incorrect working of Custom field validation in case if parameters order was changed has been fixed (352181).
-
Architectural and Support issues
-
Some misprints were fixed in the Dropout Report and in the Form Validation sections (352180, 352178).
-
June 8, 2011
The Web Forms for Marketers module 2.3.0 rev.110530 is released.
Tested with Sitecore CMS 6.5.0 rev. 110602.
Important: Web Forms for Marketers 2.3.0 is compatible with Sitecore CMS 6.5 (rev. 110602) or later. This version is not compatible with versions of Sitecore CMS earlier than 6.5.
New Features
- Web Forms for Marketers has been optimized in order to work with Sitecore CMS 6.5 and DMS 2.0. This includes:
- Utilizing the new DMS API, meaning better performance and increased extensibility.
- An Engagement Value is now associated with successfully submitted forms.
- An “Enroll in Engagement Plan” Save Action has been added, integrating with the Engagement Automation functionality in CMS 6.5 and DMS 2.0.
- Improved form reports, which are significantly faster than in previous versions.
- A new “Engagement Analytics” tab is available in the Form Reports application, which gives you access to analytics information about your form in the Executive Insight Dashboard.
- You can now upgrade your Web Forms data using the OMS v1 to v2 upgrade tool.
- Form fields and form sections can now be personalized for individual visitors based on rules using Sitecore’s Rule Set functionality fields. By default you can perform the following actions based on conditions applied to the visitor:
- Hide fields and sections.
- Insert default values from user profiles or URL query strings.
You can also use custom conditions and actions to further personalize the form.
- Two new events have been introduced, and the Form Reports have been modified to use these events.
- Form Begin indicates that a visitor has completed at least one field in a form.
- Form Dropout indicates that a session has ended without a successful submission.
- A new date picker field has been introduced.
- The Prototype javascript library used in the front-end of the module has been replaced with JQuery.
- The module now fully supports .NET v4.
Important changes
-
The “Detailed Form Failures report” has been replaced by the standard “Visit” report.
-
Detailed error statistics have been removed from the Form Usability reports and Form Failures reports in order to improve performance.
Issues resolved
-
An issue which caused issues with serializing the session state in ASP.NET’s 'StateServer' and 'SQLServer' mode has been fixed. (330466)
-
An issue which caused javascript errors when exporting forms created in the module to .ascx files has been fixed. (342235)
-
An issue which meant that field tokens could not be inserted into the message body in the Send Email Message and Send MMS actions has been fixed. (343060)
-
The Send Mail Save Action can now send messages when using an SSL connection with the mail server. (343112)
-
An issue which meant the day/moth/year labels of the Date field could not be localized if the code database was absent has been fixed. (343395, 336190,336270)
2. Known issues
The following known issues are present in the latest version of the Web Forms for Marketers:
WFFM does not work on Sitecore CMS 7.0
Reference number: 382886
If you are running Web Forms for Marketers 2.3.0 on Sitecore CMS 7.0, after opening a form on the frontend or in the Form Designer, you might encounter the error message “Could not load file or assembly 'HtmlAgilityPack, Version=1.4.0.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)”
Workaround:
- Add the following “runtime” section to the web.config file after the </configSections> tag:<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="HtmlAgilityPack" publicKeyToken="bd319b19eaf3b43a" culture="neutral" />
<bindingRedirect oldVersion="1.4.0.0" newVersion="1.4.6.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
<bindingRedirect oldVersion="3.5.0.0" newVersion="4.5.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime> - Save the changes and restart the website.
JavaScript errors when using Internet Explorer 10
Reference number: 387493
Various JavaScript errors may occur when posting forms created using WFFM module and running Internet Explorer 10.
Solution:
There are two possible solutions:
- Upgrade your WFFM version to 2.3.0 rev. 130118 or later version.
- Replace "/Website/sitecore modules/Web/Web Forms for Marketers/scripts/head.load.min.js" script with the newer version from "https://raw.github.com/headjs/headjs/v0.99/dist/head.load.min.js".
A web form cannot be submitted after upgrading WFFM 2.2.0 to WFFM 2.3.0
Reference number: 358042
If you upgraded Web Forms for Marketers module from 2.2.0 to 2.3.0 version, you may encounter the error message "We experienced a technical difficulty while processing your request. Your data may not have been correctly saved" after submitting a form. The error message in the Sitecore log file is “WARN Web Forms for Marketers: an exception: has occured while trying to execute an action.”
Workaround:
- Go to the "/sitecore/system/Modules/Web Forms for Marketers/Settings/System/System Action" folder in the master database.
- Move the “/Save Actions/Tag Action“ and “/Save Actions/Register a Goal” items to the “System Action” folder.
- Delete all sub-folders under the “System Action” folder.
- Publish the site.
Web Forms for Marketers does not fully support MVC enabled sites in Sitecore 6.6. This will be fixed in a future update.
Reference number: 378012
Currently, the Web Forms module doesn't support Sitecore MVC.
Workaround:
Web forms shouldn’t be attached to items with MVC-based presentation.
MVC-based pages can’t be opened in Page Editor after installing WFFM
Note: This known issue was fixed in Web Forms for Marketers 2.3.0 rev.130118.
Reference number: 376196
In Sitecore CMS 6.6 with installed WFFM module when you open MVC-based page in Page Editor an exception may occur.
Workaround:
- Place the “Sitecore.Support.376196.dll” file in your “bin” folder.
- Open the “App_Config\Include\forms.config” file, find the following line:
<processor type="Sitecore.Form.Core.Pipeline.InsertRenderings.Processors.GetPlaceholder, Sitecore.Forms.Core"/>
And replace it with the following one:
<processor type="Sitecore.Support.Form.Core.Pipeline.InsertRenderings.Processors.GetPlaceholder, Sitecore.Support.376196"/>
In Sitecore CMS 6.6, a web form can’t be saved after it was edited in Form Designer from Page Editor
Note: This known issue was fixed in Sitecore CMS 6.6.0 rev. 120918.
Reference number: 368711
In Sitecore CMS 6.6, when you open Form Designer from Page Editor and edit the form, there are problems when you try to save the item after that. When clicking the Save button in Page Editor, the following message appears:
"One or more items have been changed. Do you want to overwrite these changes?"
If you click “Ok”, the item is saved, but the web form changes lost.
Workaround:
Edit the web form components inline (directly on the web page) when possible or open Form Desiger from Content Editor or Sitecore Desktop.
Usability and Save Failure reports do not work in Sitecore 6.5.0 Update-4
Reference number: 362936
When the Web Forms for Marketers module is installed on 6.5 Update-4 or later, the user will get an exception "Report cannot be rendered" when the user try to run the Usability or Save Failure reports.
The full error message is as follows:
“Report /sitecore modules/shell/Web Forms for Marketers/Reports/Form Usability Report.mrt cannot be rendered : System.Data.SqlClient.SqlException: Hint 'noexpand' on object 'VisitEvents' is invalid.Statement(s) could not be prepared.”
The issue is caused by changes in DMS 2.0.1.
Workaround:
To resolve the issue, perform the following actions:
- Find the following item in the content tree:
/sitecore/system/Settings/Analytics/Reports SQL Queries/Form Visits - Remove " WITH (NOEXPAND)" from the text in the SQL field.
- Save the item.
- Repeat the steps for the following item:
/sitecore/system/Settings/Analytics/Reports SQL Queries/Form Statistics
Installation error
Reference number: 326481
If you are upgrading from Web Forms for Marketers 2.2 using the Update Installation Wizard, you may encounter an installation error: “Error installing <package name>.” An exception occurred when installing the package. If you encounter this issue try to rename the package to a shorter name and install it again. If you still experience issues please contact Sitecore Customer Service via http://support.sitecore.net (using reference number 326481).
Form Dropout tracking does not work correctly under certain conditions
Reference number: 346464
Form Dropout tracking does not work correctly if the ASP .NET sessionState variable is set to “StateServer” mode. (346464)
Send Email Action translation issue
Reference number: 313313
When you are translating a web form, in the Send Email action you cannot set unique values in the Subject and Message Body fields for each language.
Possible workaround: If you have Email Campaign Manager installed use the Send Email Campaign Message action:
- Create a new Standard Message using the Email Campaign Manager.
- Translate the message into different languages.
- Add the Send Email Campaign Message action to your web form and customize it.
Cannot enter unique values for some parameters in the Send Email Action.
Reference number: 333322
Users cannot set unique values in the "From Address” and “From Name” parameters for each web form.
Possible workaround: If you have Email Campaign Manager installed use the Send Email Campaign Message action:
- Create a new Standard Message using the Email Campaign Manager.
- Set values in the “From Address” and “From Name” parameters.
- Add the Send Email Campaign Message action to your web form and customize it.
Impossible to add a form in Page Editor when the Datasource Location is empty or contains path to a non-existent item
Reference number: 352647
If the “Datasource Location” field of the “/sitecore/layout/Renderings/Modules/Web Forms for Marketers/Form” item is empty or contains a path to a non-existent item, the form inserting functionality in Page Editor may stop working. This may happen when the “/sitecore/context/home” item is deleted or renamed, because initially the field contains the path to this item.
Workaround:
Change the “Datasource Location” field value to path to an existing item to which the most of the page editor users have the read access (for example, the site root item).
Web Forms placed on the cached sublayouts don't work.
Reference number: 354946
Web Forms placed on the sublayouts with the enabled caching do not work. It is an expected behavior. When the cached sublayout is requested Sitecore returns the cached HTML output omitting the usual ASP.NET web control life cycle. For more information about the Output Caching in Sitecore CMS, see Presentation Component Reference.
Workaround: Disable caching for sublayouts containing the web form.
"Send Email Campaign Message" save action does not work in Live mode
Reference number: 358115
The "Send Email Campaign Message" save action does not work in Live mode.
Workaround:
- Create the SendStandardMessageExt class: namespace Test
{
using Sitecore.Data;
using Sitecore.Form.Core.Client.Data.Submit;
using Sitecore.Form.Submit;
public class SendStandardMessageExt : SendStandardMessage
{
public override void Execute(ID formid, AdaptedResultList fields, params object[] data)
{
if (Sitecore.Context.Site == null)
{
return;
}
bool disableFiltering = Sitecore.Context.Site.DisableFiltering;
try
{
Sitecore.Context.Site.DisableFiltering = true;
base.Execute(formid, fields, data);
}
finally
{
Sitecore.Context.Site.DisableFiltering = disableFiltering;
}
}
}
} - Add a reference to this class in the /sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions/Send Email Campaign Message item (the Assembly and Class fields of the item)